Systems and methods for electronically signing for a delivered package

ABSTRACT

There is disclosed a method. The method includes identifying, using a mobile device, an encrypted electronic token associated with at least one physical package designated for delivery to a destination. The electronic token having been encrypted by a first key associated with a particular party. The method also includes electronically signing, using the mobile device, for the at least one physical package. This includes initiating a decryption of the encrypted electronic token with a second key associated with the particular party.

RELATED APPLICATION

This application claims priority from U.S. Provisional Application No.61/467,103, filed Mar. 24, 2011, the entire contents of which are herebyincorporated by reference.

TECHNICAL FIELD

The present disclosure generally relates to the field of computerizedsystems. More particularly, the disclosure relates to computerizedsystems and methods for signing for a delivered package.

BACKGROUND INFORMATION

Conventional systems permit a party to place an order for goods online,over the telephone, or by mail. For example, using a computer or mobiledevice, the party may access a website of a retailer, such as Amazon, toselect the desired goods and place the order. With the order, the partymay include a name and/or address to indicate to whom and where thepackage should be delivered. For example, the party may indicate his/herown name and address.

Using a delivery company, the retailer may then ship packages of theorder to the party at his/her name and/or address. In some cases, thepackages must be signed for by the party included on the order. This maybe the case, for example, if the package includes valuable, sensitive,or private goods. To ensure that an authorized party signs for thepackage, the delivery company may request that the party signing for theorder present identification. The delivery company may then transfer thepackage to the authorized party after s/he signs for it.

In some cases, however, the party receiving the package may want toremain anonymous to the delivery company to maintain his/her privacy.Moreover, some countries may have privacy laws that prohibit thedelivery company from tracking and/or checking identificationinformation of its customers. Thus, it may be important to permit anauthorized party to anonymously sign for a delivered package.

In some cases, the party receiving the package may be in a differentlocation from the location included with the order. Thus, it may beimportant to permit the receiving party to have a package delivered tohim/her based on a real-time location.

SUMMARY

In accordance with disclosed embodiments, there is provided a methodcomprising: identifying, using a mobile device, an encrypted electronictoken associated with at least one physical package designated fordelivery to a destination, the electronic token having been encrypted bya first key associated with a particular party; and electronicallysigning, using the mobile device, for the at least one physical package,including initiating a decryption of the encrypted electronic token witha second key associated with the particular party.

In accordance with disclosed embodiments, there is further provided acomputer-readable medium storing instructions, which, when executed byat least one processor, cause the at least one processor to perform amethod comprising: identifying, using a mobile device, an encryptedelectronic token associated with at least one physical packagedesignated for delivery to a destination, the electronic token havingbeen encrypted by a first key associated with a particular party; andelectronically signing, using the mobile device, for the at least onephysical package, including initiating a decryption of the encryptedelectronic token with a second key associated with the particular party.

In accordance with disclosed embodiments, there is further provided asystem comprising: a receiving mobile device configured to: identify anencrypted electronic token associated with at least one physical packagedesignated for delivery to a destination, the electronic token havingbeen encrypted by a first key associated with a particular party; andelectronically sign for the at least one physical package, includinginitiating a decryption of the encrypted electronic token with a secondkey associated with the particular party.

In accordance with disclosed embodiments, there is further provided amethod performed by a mobile device, the method comprising: identifyingan encrypted electronic token associated with at least one physicalpackage designated for delivery to a destination, the electronic tokenhaving been encrypted by a key associated with an party that isassociated with the at least one physical package.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 illustrates an exemplary system for electronically signing for adelivered package.

FIG. 2 illustrates devices of an exemplary system for electronicallysigning for a delivered package.

FIG. 3 illustrates the operations of an exemplary method performed by areceiving mobile device for electronically signing for a deliveredpackage.

FIG. 4 illustrates the operations of an exemplary method performed by adelivering mobile device for enabling electronically signing for adelivered package.

FIG. 5 illustrates an exemplary system for electronically signing for adelivered package by a receiving mobile device that is not possessed bya party identified with the order.

FIG. 6 illustrates operations of an exemplary method for electronicallysigning for a delivered package by a receiving mobile device that is notpossessed by a party identified on the order.

DETAILED DESCRIPTION

Some disclosed embodiments generally relates to electronically signingfor a package in a manner that is decoupled from the identity and/orlocation of the signing party. This may allow a party receiving thepackage to protect his/her identity. This may also afford the receivingparty the flexibility to receive the package in a location that isdifferent from a location included with the order.

In disclosed embodiments, a party who places an order for goods with aretailer has a public key and a private key, as is generally understoodin the art. The public and/or private keys may be maintained by a PublicKey Infrastructure (PKI). For example, the public key may be distributedfreely, while the private key may only be in the possession of arestricted number of users.

When the order is placed, the retailer may generate an electronic token.The electronic token may be a series of alphanumeric characters, a bitstream, a series of numbers, or any other electronic representation. Theelectronic token may be randomly-generated or may be linked tosomething, such as a biometric. For example, disclosed embodiments mayrun an algorithm, such as a hash function, on some known biometric dataof the ordering party, such as their name of fingerprint data, togenerate the electronic token.

The retailer, or some other party, may encrypt the electronic token witha public key of the ordering party. The encrypted token may appear as arandom stream of characters, such as a seemingly-random stream of 1s and0s. The encrypted token may be associated with the package. For example,the encrypted token may be printed as a barcode on the package or storedon an RFID tag on the package. Alternatively or additionally, theencrypted token may be stored on a mobile device of a party thatdelivers the package or on a host associated with the delivery companyor third party.

In some embodiments, another party, such as a party that ships and/ordelivers the package, may encrypt the electronic token. In someembodiments, the public-private key may be maintained, generated, and/orassociated with the party that ships and/or delivers the package.

The ordering party may have a private key that can unlock the encryptedelectronic token. The ordering party may share the private key withanother party, such as a receiving party, permanently or for a limitedamount of time. The receiving party may determine that the package isout for delivery. The receiving party may indicate that a partydelivering the package should deliver it to a current location of thereceiving party, or some other location, instead of a location listedwith the order.

The delivering party may alter his/her delivery route to deliver thepackage to a location of the receiving party, for example. Thedelivering party may “check-in” at a delivery location, for example,with the receiving party. For example, the delivering party may engagein a near field communication (NFC) “bump” with the receiving party'smobile device to verify that the delivering party has arrived at theexact location of the receiving party. In some embodiments, thedelivering party may check-in at a delivery location by, for example,engaging in NFC communications with a fixed NFC tag. The NFC bump may,in some embodiments, transfer the encrypted electronic token to thereceiving mobile device. The receiving mobile device may receive theencrypted electronic token from a host, or may not receive the encryptedelectronic token at all in some embodiments. The receiving mobile devicemay initiate decryption of the electronic token. When the electronictoken is successfully decrypted, then the receiving party may beconsidered to have executed an electronic signature and the deliveringparty may leave the package in possession of and/or accompanying thereceiving party.

The term “NFC bump” is commonly-understood in the art, and may refer tobringing two NFC-capable devices together, for example, where one actsas a NFC reader/writer and the other acts as a NFC tag for the purposeof exchanging information. The device acting as a tag, may be a smartphone emulating a NFC tag. In some embodiments, both devices may havereader/writer functionality, and one may initiate pushing information tothe other or attempting to receive information from the other, as thoughthe other device is a fixed NFC tag. And in some embodiments adelivering mobile device may check-in at a delivery location using afixed NFC tag instead of via an NFC bump.

As used herein, the term “party” is intended to apply broadly to anindividual, group, or corporate entity that may order, deliver, orotherwise participate in the order, fulfillment, or delivery of apackage.

In one example embodiment, one or more mobile devices, such as adelivering mobile device, may be associated with a package; in otherwords, the one or more mobile devices may be placed within a package,attached to a package, or otherwise placed within a vicinity of thepackage. In disclosed embodiments, the package may be a physical packagedesignated for delivery to a destination.

The precise location of a mobile devices in relation to the package(within, attached, within the vicinity, or in close proximity, forexample) may not matter; what matters is that in some embodiments, theone or more mobile devices can effectively collect the particular typeof information associated with the package and/or its contents. Forexample, this sensor-collectable information may include geographiclocation information associated with the package at any given time. Forpurposes of this disclosure, a container or package may be a box,envelope or any other media used to ship documentation or products fromone point to another. “Goods” may refer to the item(s) in the containeror package.

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings. Whereverpossible, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

FIG. 1 illustrates system 100 for electronically signing for a deliveredpackage. System 100 may include receiving mobile device 102, deliveringmobile device 104, and/or host 106, connected via network 108. Receivingmobile device 102 may be in possession of and/or accompanying a partyreceiving a shipped package, while delivering mobile device 104 may bein possession of and/or accompanying a party delivering the shippedpackage. Host 106 may be associated with a third-party applicationrunning on receiving mobile device 102 and/or delivering mobile device104. In some embodiments, host 106 may be associated with a deliverycompany and may store data relating to delivery of the package.

Network 108 may be a shared, public, or private network, may encompass awide area or local area, and may be implemented through any suitablecombination of wired and/or wireless communication networks.Furthermore, network 108 may comprise a local area network (LAN), a widearea network (WAN), an intranet, or the Internet. Network 108 may be acloud network, a mesh network, or some other kind of distributednetwork. In some embodiments, some combination of receiving mobiledevice 102, delivering mobile device 104, and/or host 106 may bedirectly connected, via a wired or wireless connection, instead ofconnecting through network 108.

Delivering mobile device 104 may accompany a party delivering a packageto a designated destination. Delivering mobile device 104 may collectlocation information, and may publish that location information via host106. For example, delivering mobile device 104 may periodically send itslocation to host 106.

Receiving mobile device 102 may track the location of the package byinterrogating host 106 on the whereabouts of delivering mobile device104. Receiving mobile device 102 may also determine from host 106whether the package is in transit to its designated destination, out fordelivery, and/or when the package is expected to be shipped ordelivered. In general, receiving mobile device 102 may retrieve varioustypes of information associated with the order or shipment of thepackage from host 106. In some embodiments, receiving mobile device 102may receive information directly from delivering mobile device 104.

Delivering mobile device 104 may be en route to delivering the packageto an address or location designated with the order. While deliveringmobile device 104 is en route, receiving mobile device 102 may indicateto host 106 that it would like delivering mobile device 104 to deliverthe package to a current location of mobile device 104 or some otherlocation. Delivering mobile device 104 then take an alternative route todeliver the package to the new designated location.

At delivery, delivering mobile device 104 may check-in at a deliverylocation, for example, with receiving mobile device 102, and may causean encrypted electronic token to be transferred to receiving mobiledevice 102. Receiving mobile device 102 may decrypt the electronictoken, thereby anonymously signing for the package.

System 100 is exemplary, and the number and distribution of the variousentities shown may be different depending on specific embodiments. Forexample, the components in system 100 may be combined and/or distributedover multiple entities, including other computers, handheld computers,mobile phones, tablet computers, or other computing platform. Thus, theconfiguration described in system 100 is an example only and is notintended to be limiting.

FIG. 2 illustrates devices of an exemplary system 200 for electronicallysigning for a delivered package. System 200 may include mobile device202 and host 204. Mobile device 202 may be similar to receiving mobiledevice 102 and/or delivering mobile device 104 from FIG. 1, and host 204may be similar to host 106. Both mobile device 202 and host 204 mayinclude general-purpose computing components configured to executespecial-purpose instructions or code to perform certain actions.

Mobile device 202 may include detecting portion 206, which may includeone or more software and/or hardware components for collecting data,such as environmental data. For example, detecting portion 206 maycollect location information about itself. In some embodiments, locationinformation may include the use of a Global Positioning System (GPS).Alternately, location information may be determined through cellulartriangulation, wireless network association, the capture of fixedlocation scan, an NFC bump, or the capture of mobile location scan. Someexemplary aspects of mobile device 202 are described in U.S. applicationSer. Nos. 13/351,861 and 13/351,852, the entire contents of which arehereby incorporated by reference.

Mobile device 202 may also include central processing unit (CPU) 208 andmemory 210 to process data, such as the collected environmental data,inputted data, or data retrieved from a storage device. CPU 208 mayinclude one or more processors configured to execute computer programinstructions to perform various processes and methods. CPU 208 may readthe computer program instructions from memory 210 or from anycomputer-readable medium. Memory 210 may include random access memory(RAM) and/or read only memory (ROM) configured to access and storeinformation and computer program instructions. Memory 210 may alsoinclude additional memory to store data and information and/or one ormore internal databases to store tables, lists, or other datastructures.

Mobile device 202 may include I/O Unit 212 for sending data over anetwork or any other medium. For example, I/O Unit 212 may send dataover a network, point-to-point, and/or point-to-multipoint connectioneither wirelessly or over a cable.

Host 204 may include a CPU 214 and/or a memory 216, which may be similarto CPU 208 and memory 210 from mobile device 202. Host/Storage Device204 may also include database 218. Database 218 may store large amountsof data, and may include a magnetic, semiconductor, tape, optical, orother type of storage device. In some embodiments, database 218 maystore historical data for auditing purposes. Host/storage device 204 mayinclude an I/O Unit 220 for communicating with mobile device 202. I/OUnit 220 may be similar to I/O Unit 212 on mobile device 202.

System 200 is exemplary only, and the number and distribution of thevarious entities shown may be different depending on specificembodiments. For example, in some embodiments, mobile device 202 may notinclude detecting portion 206, CPU 208, and/or memory 210. In someembodiments, host 204 may be distributed over multiple entities,including other distribution systems, sensors, computers, handheldcomputers, mobile phones, tablet computers, or other computing platform.Mobile device 202 may similarly be implemented or distributed over anycomputing platform. Thus, the configuration described in system 200 isan example only and is not intended to be limiting.

FIG. 3 illustrates the operations of an exemplary method 300 that may beperformed by receiving mobile device 102 for electronically signing fora delivered package. Method 300 may be executed by CPU 208 on receivingmobile device 102. Method 300 may also be performed in conjunction withother components shown or not shown in system 100. As explained, in someimplementations, some steps in method 300 are optional and can berearranged. Additional steps can also be added to method 300.

To begin, receiving mobile device 102 may identify a package as being intransit (step 302). For example, receiving mobile device 102 may receivea notification from host 106 that the package is out for delivery to adesignated destination. Host 106 may be monitoring the status ofdelivering mobile device 104 to determine its location and whether ornot it is associated with the package. When host 106 determines that thepackage is out for delivery with delivering mobile device 104, it maysend the notification to receiving mobile device 102.

Next, receiving mobile device 102 may send a message to host 106,requesting that the package be delivered to a location of receivingmobile device 102 (step 304). For example, a party in possession ofand/or accompanying receiving mobile device 102 may be out to lunch, andmay want the package delivered to his/her current location instead of alocation designated with the original order. In disclosed embodiments,receiving mobile device 102 may specify its current location fordelivery if it determines that the package will be delivered within acertain amount of time (e.g., 30 minutes), for example. Alternatively,receiving mobile device 102 may specify another location for delivery ifthe package will be delivered at a later time (e.g., in 2 hours), forexample. In this way, receiving mobile device 102 may dynamically adjustthe delivery location based on real-time circumstances. In someembodiments, the delivery company may charge extra for a change indelivery location.

Receiving mobile device 102 may then determine whether or not thepackage is ready to be received (step 306). For example, receivingmobile device 102 may receive a notification from host 106 thatdelivering mobile device 104 is within a predetermined distance or timeperiod from receiving mobile device 102. This determination may be madein accordance with GPS information. For example, host 106 may monitorthe location of delivering mobile device 104 and send a notification toreceiving mobile device 102 when the location information (such as GPScoordinates) show delivering mobile device 104 at the same or similarGPS coordinates as receiving mobile device 102. For example, host 106may notify receiving mobile device 102 that the package is ready to bereceived when delivering mobile device 104 is near the front door or theloading dock.

If the package is not ready to be received, then receiving mobile device102 keeps checking until the package is ready to be received. If thepackage is ready to be received, then receiving mobile device 102 mayenable delivering mobile device 104 to check-in at a delivery location,for example, at receiving mobile device 102 (step 308). This may be doneusing a form of location tracking that is more precise than GPS. Forexample, delivering mobile device 104 may exchange short-range messageswith receiving mobile device 102, such as via Bluetooth, an NFC bump,and/or a barcode scan. The check-in may ensure that a delivery partyactually delivers the package directly to a delivery location and/orreceiving party. Receiving mobile device 102 may send a confirmation ofthe check-in to host 106. In this way, host 106 can ensure that thedelivering party delivered the package at the location requested by therecipient.

Next, receiving mobile device 102 may access an encrypted electronictoken associated with the package (step 310). For example, during thecheck-in, delivering mobile device 104 may transfer the encryptedelectronic token to receiving mobile device 102. Alternatively oradditionally, receiving mobile device 102 may scan or read the encryptedelectronic token from the package, such as from a barcode or an RFIDtag. In some embodiments, host 106 may send the encrypted electronictoken to receiving mobile device 102 via network 108 or otherwise,either at the time of check-in or beforehand, such as at the time theproduct was ordered.

The encrypted electronic token may have been encrypted by a public keyassociated with a particular party, such as a party who placed theoriginal order, or some other party. Because the key may be public, itmay have been accessible to the retailer, for example, who may havegenerated a token and encrypted the generated token when the order wasplaced or shipped, or at any other time.

Receiving mobile device 102 may then electronically sign for the packageby decrypting the encrypted token (step 312). For example, receivingmobile device may possess a corresponding private key of a theparticular party. The private key may be able to undo the encryption ofthe token that was performed using the public key. Thus, receivingmobile device 102 may be able to decrypt the encrypted electronic tokento determine the original electronic token. Receiving mobile device 102may send the decrypted electronic token to host 106 to verify that aparty in possession of and/or accompanying receiving mobile device 102is authorized to receive the package.

Receiving mobile device 102 may require additional security measuresfrom a party that possesses it, so that the party may electronicallysign for the package. For example, receiving mobile device 102 mayrequire a password or biometric scan to permit a party to utilize thefunctionality described herein, including the ability to electronicallysign for a package. The private key may itself be transferred inencrypted mode and never be directly accessible by the user. Instead,the private key may only be accessible to an application running onreceiving mobile device 102 and/or host 106. For example, theapplication may be running in a protected area on mobile device 102and/or host 106.

When receiving mobile device 102 sends the decrypted electronic tokenback to host 106, and if the decrypted electronic token matches theoriginal unencrypted token, then host 106 may verify that the partyreceiving the package is authorized. Host 106 may have to communicatewith some other party, such as a retailer, to verify that the decryptedtoken matches the original unencrypted token. In this way, host 106 maynever need to collect identity information of a receiving party, whichwould protect the privacy of the receiving party and may ensurecompliance with local laws.

Next, receiving mobile device 102 may release payment associated withthe packages (step 314). For example, the order may have been structuredto use cash on demand (COD) payment. Thus, when the electronic signatureis verified and the delivering party transfers possession of the packageto the receiving party, payment can be transferred. In some embodiments,the receiving party may have a chance to inspect the package beforeconfirming that the payment be transferred. This may give the receivingparty an opportunity to determine whether the product is damaged. Method300 may then end.

FIG. 4 illustrates the operations of an exemplary method 400 performedby a delivering mobile device 104 for enabling electronically signingfor a delivered package. Method 400 may be executed by CPU 208 ondelivering mobile device 104. Method 400 may also be performed inconjunction with other components not shown in system 100. As explained,some steps in method 400 are optional and can be rearranged. Additionalsteps can also be added to method 400.

Method 400 begins when delivering mobile device 104 receives a requestthat a package be delivered to a location of receiving mobile device 102(step 402). Delivering mobile device 104 may receive this request fromhost 106, which in turn may have received the request from receivingmobile device 102. In some embodiments, delivering mobile device 104 mayreceive the request from receiving mobile device 102 directly or viaanother party. When delivering mobile device 104 receives this message,it may already be in transit. For example, delivering mobile device 104may be travelling with a delivering party that is out for delivery witha plurality of packages, including the package to be delivered to alocation of receiving mobile device 102. In one example, the deliveringparty may be a driver in possession of and/or accompanying deliveringmobile device 104. The delivering party may have many packages inhis/her truck for delivery in a shift, such as in one day. The packagesin the truck may be linked with delivering mobile device 104. In thisway, a location of the packages and of the delivering party can bemonitored using location information collected by delivering mobiledevice 104.

Delivering mobile device 104 may then interrupt a pre-planned deliveryroute and set a destination as the location received from receivingmobile device 102 (step 404). For example, delivering mobile device 104may have intended to deliver the package to a location on the packageorder, but may revise a pre-planned route so that the package may bedelivered at the location specified by the receiving mobile device 102.Delivering mobile device 104 may immediately deliver the package to alocation of receiving mobile device 102 or may do so at a later timedepending on one or more factors such as: timing of delivery informationprovided by receiving mobile device 102, traffic conditions, weatherconditions, etc.

Delivering mobile device 104 may then determine whether or not thepackage is ready to be delivered (step 406). For example, deliveringmobile device 104 may determined that the package is ready to bedelivered when it arrives a location of the receiving mobile device 102.If delivering mobile device 104 determines that the package is not yetready to be delivered, then it continues to check.

Alternatively, if the delivering mobile device 104 determines that thepackage is ready to be delivered, then delivering mobile device 104 maycheck-in at a delivery location, for example, at receiving mobile device102 (step 408). For example, delivering mobile device may exchange ashort distance message with receiving mobile device 102, such as aBluetooth message, NFC bump, or RFID scan, to confirm that it deliveredthe package to the receiving party and not just in a nearby vicinity.

In some embodiments, delivering mobile device 104 may check-in at an NFCstationary tag. The stationary tag may be located, for example, at aloading dock, door, or other location. The delivering mobile device 104may write to the NFC tag to create a record that it checked-in at thelocation of the NFC tag. Alternatively or additionally, the deliveringmobile device 104 may read from the NFC tag.

Next, delivering mobile device 104 may optionally forward an encryptedelectronic token to receiving mobile device 102 (step 410). This mayoccur as part of the NFC bump, for example, as part of the check-inprocess. In other embodiments, delivering mobile device 104 may notforward this encrypted electronic token, and receiving mobile device mayreceive the encrypted electronic token in some other way. In someembodiments delivering mobile device 104 may not forward the encryptedelectronic key, and receiving mobile device 102 may gain access to it insome other way, for example, via host 106. Thus, in some embodimentsdelivering mobile device 104 may not even have access to the encryptedelectronic token.

Receiving mobile device 102 may initiate decryption of the encryptedelectronic token, and host 106 may verify that the decryption wassuccessfully executed. Thus, delivering mobile device 104 may receiveconfirmation that the receiving mobile device correctly decrypted theelectronic token, for example, from host 106 (step 412). This is anindication to delivering mobile device 104 that receiving mobile device102 has successfully electronically signed for the package. Thus,delivering mobile device 104 may indicate to the delivering party thatthe shipment is complete and then he/she can transfer possession of thepackage to the receiving party and depart.

In some embodiments, receiving mobile device 102 may release paymentupon confirmation that the electronic signature was accepted by host106. Thus, delivering mobile device may receive an indication from host106 that payment was released. In some embodiments, delivering mobiledevice 104 may not transfer possession of the package unless payment isfirst released by the receiving party. Method 400 may then end.

As discussed, a delivered packaged may be electronically signed by aparty who does not have to provide any personally-identifiableinformation such as his/her name, fingerprints, or other biometrics.Instead, the receiving party may only needs to have access to a privatekey in order to decrypt an electronic token associated with the package.The electronic token may have been encrypted by a public key of a partythat ordered goods in the package. The private key therefore, may be thecompliment of the public key, in that it may be able to decrypt theencryption performed using the public key. Possession of the private keymay be tightly controlled. In this way, a receiving party can prove thathe/she is linked to the ordering party and is authorized to receive thepackage by virtual of the fact that s/he has access to the private key.And the receiving party can prove that he/she has access to the privatekey by enabling the decryption of the encrypted token, which generallyonly the private key can accomplish.

Thus, in some embodiments, the party receiving the package may bedifferent from the party who ordered the package. For example, the partyordering the package may share his/her private key with the partyreceiving the package to ensure that the receiving party is authorizedto receive it.

FIG. 5 illustrates an exemplary system 500 for electronically signingfor a delivered package by a receiving mobile device that is notpossessed by a party identified with the order. System 500 may includeordering device 502, receiving mobile device 504, and/or deliveringmobile device 506. Receiving mobile device 504 may be similar toreceiving mobile device 102 from FIG. 1. Similarly, delivering mobiledevice 506 may be similar to delivering mobile device 104.

System 500 may also include courier host 508, third party applicationhost 510, and/or seller host 512. Ordering device 502, receiving mobiledevice 504, delivering mobile device 506 courier host 508, third partyapplication host 510, and/or seller host 512 may be connected directlyof via network 514. Network 514 may be similar to network 108 from FIG.1.

An ordering party may place an order for goods from seller host 512,using ordering device 502. Ordering device 502 may be any type ofcomputing device, such as a desktop, laptop, tablet, or mobile phone,for example. The ordering party may be associated with a private key anda public key. The private key may only be accessible to the orderingparty and other parties to whom the ordering party grants permission.The public key, however, may be managed by a PKI and may be publiclyavailable.

Thus, after the order is made, seller host 512 may have access to thepublic key of the ordering party. The seller device may generate atoken, such as a string of letters and/or numbers, and may encrypt thetoken using the public key of the ordering device. Seller host 512 maypass the original token and/or the encrypted token to third partyapplication host 510 and/or courier host 508. Courier host 508 mayinclude the encrypted electronic token on the package as a barcodeand/or may forward the encrypted electronic token to delivering mobiledevice 506.

When ordering device 502 places the order, it may indicate an addressfor delivery. In some embodiments, ordering device 502 may indicate thatthe package must be signed for before it is transferred to a receivingparty. The ordering party may itself receive the package, or maydelegate another party to receive the package. To delegate the otherparty, the ordering party may need to ensure that the receiving partyhas access to the private key of the ordering party.

Therefore, the ordering party may provide authorization to the receivingparty by electronically transferring the private key to receiving mobiledevice 504. In some embodiments, the private key may itself be stored inan encrypted format. And in some embodiments, the private key may onlybe usable for a limited amount of time or a limited number of uses.

In some embodiments, the private key may be maintained on a remoteserver, such as third party application host 510. In that case, orderingdevice 502 may ensure that receiving mobile device 504 is able to accessthe private key or initiate a decryption using the private key stored onthird party application host 510.

Third party application host 510 may be involved in enabling theelectronic signature of the package. In some embodiments, third partyapplication host may be involved or linked with an organization thatcreated an application running on receiving mobile device 504 and/ordelivering mobile device 506.

After receiving mobile device 504 becomes authorized to receive thepackage, it may electronically sign for the package at delivery. Forexample, receiving mobile device 504 may gain access to the encryptedelectronic token, and may decrypt the encrypted electronic token. Insome embodiments, the decryption may occur on receiving mobile device504, while in other embodiments, receiving mobile device 504 may causethe decryption to occur on third party application host 510.

FIG. 6 illustrates operations of an exemplary method 600 forelectronically signing for a delivered package by a receiving mobiledevice 504 that is not possessed and/or is not operated by a partyidentified on the order. Method 600 may be executed by CPU 208 and/or214 on some combination of ordering device 502, receiving mobile device504, and third party application host 510, for example. Method 600 mayalso be performed in conjunction with other components not shown insystem 500. As explained, some steps in method 600 are optional and canbe rearranged. Additional steps can also be added to method 600.

To begin, ordering device 502 may access seller host 512 to order apackage (step 602). Seller host 512, using a public key associated withthe ordering party, may generate and encrypt a token when the order ismade. Seller host 512 may forward the encrypted and unencrypted tokensto courier host 508. The encrypted electronic token may be passed toreceiving mobile device 504, courier host 508, and/or third partyapplication host 510. And the unencrypted electronic token may beforwarded to courier host 508 in order to verify decryption of theencrypted electronic token.

Next, ordering device 502, may authorize receiving mobile device 504 toreceive the package (step 604). For example, ordering device 502 mayelectronically transfer its private key to receiving mobile device 504.In disclosed embodiments, ordering device 502 may authorize receivingmobile computer 504 to access the private key on third party host 510,or instruct third party host 510 to perform decryption if the privatekey is stored on third party application host 510.

Receiving mobile device 504 may be possessed, accompanied, and/oroperated by a party different from the ordering party. Receiving mobiledevice 504 may be possessed, accompanied, and/or operated by a partydifferent from any party associated with the order as well. The identityof party that possesses, accompanies, and/or operates receiving mobiledevice 504 may be unknown by the retailer, the delivery company, and/orthe ordering party.

Next, the receiving mobile device 504 may determine whether the packageis in transit, for example, by querying courier host 508 (step 606). Forexample, receiving mobile device 504 may determine that the package isout on the truck for delivery that day. When the package is determinedto be in transit, receiving mobile device 504 may send locationinformation to courier host 508 (step 608). The location information mayindicate a location at which receiving mobile device 504 can receive thepackage.

Receiving mobile device 504 then determines if the package is ready tobe received (step 610). For example, receiving mobile device 504 mayreceive an indication from courier host 508 that delivering mobiledevice 506 is approaching or is at the location indicated by receivingmobile device 504 at step 608, for example.

If the package is ready to be received, then receiving mobile device 504may enable delivering mobile device 506 to check-in at a deliverylocation, for example, receiving mobile device 504 using an NFC bump,Bluetooth message, or RFID scan (step 612), for example. Next, receivingmobile device 504 may access an encrypted electronic token associatedwith the package, and may forward the encrypted electronic token tothird party application host 510 (step 614). Third party applicationhost 616, upon receipt of the encrypted electronic token, may determinethat receiving mobile device 504 is authorize to instruct decryption.Thereafter, third party application host 616 may decrypt the electronictoken with a private key of the ordering party (step 616).

Third party application host 616 may then send a message to courier host508 with the decrypted token. If the decrypted token matches theoriginal token before it was encrypted, then courier host may determinethat the package has been electronically signed for by an authorizedparty.

In some embodiments, the decryption make occur on receiving mobiledevice 504 instead of third party application host 510. In that case,receiving mobile device 504 would send the decrypted token to courierhost 508, for example, to verify that it matches the originalunencrypted token generated by seller host 512, for example. Method 600may then end.

While certain features and embodiments of the invention have beendescribed, other embodiments of the invention will be apparent to thoseskilled in the art from consideration of the specification and practiceof the embodiments of the invention disclosed herein. Furthermore,although aspects of embodiments of the present invention have beendescribed in part as software, computer-executable instructions, and/orother data stored in memory and other storage mediums, one skilled inthe art will appreciate that these aspects can also be stored on or readfrom other types of tangible, non-transitory computer-readable media,such as secondary storage devices, like hard disks, floppy disks, or aCD-ROM, or other forms of RAM or ROM. Further, the steps of thedisclosed methods may be modified in various ways, including byreordering steps and/or inserting or deleting steps, without departingfrom the principles of the invention.

It is intended that the specification and examples be considered asexemplary only, with a true scope and spirit of the invention beingindicated by the following claims.

What is claimed is:
 1. A method comprising: receiving, at a mobiledevice, authorization to receive delivery of at least one physicalpackage ordered by a particular party and being sent to a firstlocation, wherein receiving the authorization includes receiving, afterthe particular party orders the at least one physical package, a privatekey associated with the particular party; transmitting a request thatthe at least one physical package be delivered to a second location thatis different than the first location while the at least one physicalpackage is in transit to the first location; identifying, using themobile device, at the second location, an encrypted electronic tokenassociated with the at least one physical package, the electronic tokenhaving been encrypted by a public key associated with the particularparty; and electronically signing, using the mobile device, for the atleast one physical package, including decrypting the encryptedelectronic token using the private key associated with the particularparty.
 2. The method of claim 1, wherein the private key is stored onthe mobile device in a protected format.
 3. The method of claim 1,wherein the particular party is different from a receiving partyassociated with the mobile device when the mobile device electronicallysigns for the at least one physical package.
 4. The method of claim 1,wherein electronically signing for the at least one physical packagecompletes delivery of the at least one physical package.
 5. The methodof claim 1, wherein the requesting causes the second party to deviatefrom a planned delivery route.
 6. The method of claim 1, furthercomprising: releasing a payment associated with the at least onephysical package upon electronically signing for the at least onephysical package.
 7. The method of claim 1, further comprising: enablinga second party delivering the at least one physical package to check-inat a delivery location using a delivering mobile device.
 8. The methodof claim 7, wherein the check-in comprises at least one of a near fieldcommunication (NFC) bump or a Bluetooth message between the mobiledevice and the delivering mobile device.
 9. The method of claim 7,further comprising: receiving the encrypted electronic token from thedelivering mobile device during the check-in.
 10. A non-transitorycomputer-readable storage medium storing program instructions, which,when executed by at least one processor, cause the at least oneprocessor to perform a method comprising: receiving, at a mobile device,authorization to receive delivery of at least one physical packageordered by a particular party and being sent to a first location,wherein receiving the authorization includes receiving, after theparticular party orders the at least one physical package, a private keyassociated with the particular party; transmitting a request that the atleast one physical package be delivered to a second location that isdifferent than the first location while the at least one physicalpackage is in transit to the first location; identifying, using themobile device, at the second location, an encrypted electronic tokenassociated with the at least one physical package, the electronic tokenhaving been encrypted by a public key associated with the particularparty; and electronically signing, using the mobile device, for the atleast one physical package, including decrypting of the encryptedelectronic token using the private key associated with the particularparty.
 11. The computer-readable medium of claim 10, wherein the privatekey is stored on the mobile device in a protected format.
 12. Thecomputer-readable medium of claim 10, wherein the particular party isdifferent from a receiving party that is associated with the mobiledevice when the mobile device electronically signs for the at least onephysical package.
 13. The computer-readable medium of claim 10, whereinelectronically signing for the package completes delivery of the atleast one physical package.
 14. The computer-readable medium of claim10, wherein the requesting causes the second party to deviate from aplanned delivery route.
 15. The computer-readable medium of claim 10,the method further comprising: releasing a payment associated with theat least one physical package upon electronically signing for the atleast one physical package.
 16. The computer-readable medium of claim10, the method further comprising: enabling a second party deliveringthe at least one physical package to check-in at a delivery locationusing a delivering mobile device.
 17. The computer-readable medium ofclaim 16, wherein the check-in comprises at least one of a near fieldcommunication (NFC) bump or a Bluetooth message between the mobiledevice and the delivering mobile device.
 18. The computer-readablemedium of claim 16, the method further comprising: receiving theencrypted electronic token from the delivering mobile device during thecheck-in.
 19. A system comprising: a receiving mobile device comprisingat least one processor; and a memory storing software instructions, thatwhen executed by at least one processor cause the at least one processorto perform operations including: receiving authorization to receivedelivery of at least one physical package ordered by a particular partyand being sent to a first location, wherein the authorization includesreceiving, after the particular party orders the at least one physicalpackage, a private key associated with the particular party;transmitting a request that the at least one physical package bedelivered to a second location that is different than the first locationwhile the at least one physical package is in transit to the firstlocation identifying, at the second location, an encrypted electronictoken associated with the at least one physical package, the electronictoken having been encrypted by a public key associated with theparticular party; and electronically signing for the at least onephysical package, including decrypting of the encrypted electronic tokenusing the private key associated with the particular party.
 20. Thesystem of claim 19, wherein the receiving mobile device is furtherconfigured to store the private key in a protected format.
 21. Thesystem of claim 19, wherein the particular party is an ordering party,the system further comprising: an ordering device configured to orderthe at least one physical package according to user input from theordering party, wherein the ordering party is different from a receivingparty that is associated with the receiving mobile device when thereceiving mobile device electronically signs for the at least onephysical package.
 22. The system of claim 19, wherein electronicallysigning for the package completes delivery of the at least one physicalpackage.
 23. The system of claim 19, wherein the delivering mobiledevice is configured to: generate a new delivery route that deviatesfrom a previously-planned delivery route.
 24. The system of claim 19,wherein the receiving mobile device is further configured to: release apayment associated with the package upon electronically signing for theat least one physical package.
 25. The system of claim 19, furthercomprising a delivering mobile device configured to check-in at adelivery location.
 26. The system of claim 25, wherein the check-incomprises at least one of a near field communication (NFC) bump or aBluetooth message between the receiving mobile device and the deliveringmobile device.
 27. The system of claim 25, wherein the receiving mobiledevice is further configured to receive the encrypted electronic tokenfrom the delivering mobile device during the check-in.